Note: Where you see local paths specified, be sure to use the path appropriate for your system, such as C:\Program Files (x86)\ for C:\Program Files\.
Note: This procedure uses specific names for folders and aliases that you create during the procedure, such as ASI_2 and iMIS_2. You can substitute meaningful, unique names in place of these.
1. Create a new copy of the ASI folder structure and modify the access control lists for the new copy.
□ In C:\Program Files, create a copy of the entire ASI folder and all of its sub-folders, giving the new folder a unique name, such as ASI_2.
xcopy "\Program Files\ASI" "\Program Files\ASI_2" /e /i /s
□ Modify the access control lists for the new folder by running the following against it from a command line:
ICACLS "\Program Files\ASI_2" /t /grant Users:F
ICACLS "\Program Files\ASI_2\iMIS\Net" /t /grant "Network Service":F
2. Define new virtual directories in Internet Information Services (IIS) and point them to new instances of the iMIS applications installed on this appserver.
□ IIS7: In IIS, expand the Default Web Site. If iMIS and/or iMISpublic appears under Default Web Site, perform the following steps for each site:
■ Right-click Default Web Site and select Add Virtual Directory.
■ Specify a unique Alias (iMIS_2 or iMISpublic_2) and Path (C:\Program Files\ASI_2\iMIS\net or C:\Program Files\ASI_2\iMIS\iMIS_public).
■ Right-click the new virtual directory and select Convert to Application.
■ In the pop-up dialog, click Select… and specify iMISapp; click OK.
■ In the left pane, click Application Pools (above Sites > Default Website). In the main pane, double-click iMISapp: Ensure that .Net Framework 4.0 is selected, Managed pipeline mode is set to Integrated, and Start application pool immediately is checked. Click OK.
■ Select your new application node (iMIS_2 or iMISpublic_2); under IIS settings in the main pane, double-click the Error Pages icon, then double-click the entry for the 404 status code. Select Execute a URL on this site, and edit the URL to refer to the 404.aspx page under the new application's alias (/iMIS_2/404.aspx or /iMISpublic_2/404.aspx). Click OK.
■ With the new application node still selected, double-click the Default Document icon under the IIS settings. If there is no entry for Default.aspx, add it.
■ Verify that NetTcp is enabled: In IIS Manager, select the site, and select Advanced Settings. Ensure that net.tcp appears in Enabled Protocols.
□ IIS6: In IIS, expand the Default Web Site. If iMIS and/or iMISpublic appears under Default Web Site, perform the following steps for each site:
■ Right-click Default Web Site and select New > Virtual Directory.
■ Using the wizard, specify a unique Alias (iMIS_2 or iMISpublic_2), the Path (C:\Program Files\ASI_2\iMIS\net or C:\Program Files\ASI_2\iMIS\iMIS_public), and allow only Read permissions.
■ Right-click the new virtual directory and select Properties.
■ On the Virtual Directory tab, click Create next to the Application name field.
■ From Execute permissions, select Scripts only.
■ From Application pool, select iMISASP20 (Windows 2003) or Classic .NET AppPool (Windows 2008).
■ On the ASP.NET tab, for the ASP.NET version, select 4.0.x.
■ On the Custom Errors tab, select 404 HTTP Error configuration and click Edit. Change Message type to URL and URL to a slash followed by the virtual directory name followed by /404.aspx (/iMIS_2/404.aspx or /iMISpublic_2/404.aspx).
■ On the HTTP Headers tab, click Add next to the Custom HTTP headers field. In the Custom header name field, insert X-UA-Compatible. In the Custom header value field, insert IE=EmulateIE8.
■ On the Documents tab, select the Enable default content page option and Add the Default.aspx file at the top of the documents (unless it already appears there).
■ Click OK. The icon for the virtual directory (iMIS_2 or iMISpublic_2) changes to a gear icon to signify that it is now an ASP.NET application.
3. Create an iMIS database for use with the new instance of iMIS.
□ Use your SQL Server management tools to create a new iMIS database to use with this new instance of iMIS. (Generally, you do this by restoring a backup of your original instance of iMIS.)
□ Launch DB Maintenance, the DBMaintenance.exe utility that is located in the new ASI_2 folder structure (C:\Program Files\ASI_2\iMIS\net\iMISDBUpgrade).
□ Use the iMIS SQL Server login credentials to connect to the new iMIS database for this instance of iMIS.
□ When the iMIS Database Repair window appears, click Prepare iMIS Database to create the correct SQL Logins.
Tip: Every time you restore an iMIS database under a new name, remember to run Prepare iMIS Database to create SQL Logins, or no one will be able to log into iMIS Desktop.
4. Configure the new instance of iMIS using the Multi-Instance Utility.
□ Locate and run the AsiMultiInstanceUtility.exe utility. Default location: \Program Files\ASI\iMIS\Net\bin
□ In iMIS Installation File Path, enter the full path to the iMIS subfolder located within the new ASI_2 folder (C:\Program Files\ASI_2\iMIS).
□ In Virtual Directory Name, specify the URL for the new iMIS_2 application that you created earlier (for example, http://(servername)/iMIS_2).
□ In SMTP Server, specify the domain name of your organization's SMTP server.
□ In SQL Server Name, Database name, Login, and Password, specify the location of the new iMIS database and the iMIS SQL Server login credentials for that SQL Server instance.
□ In Original DB Name, enter the value for the database from which the copy was made.
□ (optional) Enable Encrypt web.config files to encrypt the web.config files used by the iMIS applications. (See Encrypt and Decrypt sections of .NET web.config files.)
□ If needed, override the default names for the ODBC DSN and services set by the utility.
□ For an initial install of a second instance, leave Configure services enabled.
□ Verify that the Publish, Workflow, and SOA Host services for all other instances are running, then click Reconfigure iMIS site.
□ If reconfiguration stops and Remove Indexing Catalog is enabled, click it before proceeding. Once the conflicting Indexing Service catalog is removed, run Reconfigure iMIS site again. See Removing the indexing catalog (Indexing Service).
□ The utility displays status information as it updates .config files, updates the SystemConfig table in the database, creates an ODBC DSN entry for the new database instance, creates AsiWorkflow15_(dbname), AsiPublishing15_(dbname), and AsiSoaHost15_(dbname) services, and creates a new Indexing Service catalog for the new instance of iMIS. The message Configuration Successful appears on completion.
5. Assign full permissions to the BODAssembly.dll.
□ Navigate to the folder containing the BODAssembly.dll file. Each iMIS site has its own BODAssembly.dll, which is usually located in C:\Windows\Temp\iMIS site name.
□ Change the permissions to Full control:
■ Run the following command line:
ICACLS “C:\Windows\Temp\This is your sitename\BODAssembly.dll” /grant NetworkService:F
or
■ Right-click on the BODAssembly.dll file and select Properties. Select the Security tab and click . Select the same user as the IIS AppPool and assign Full control.
□ Restart IIS.
6. Using Control Panel > Services, view the services running on the appserver and verify that the new AsiWorkflow15_(dbname), AsiPublishing15_(dbname), and (if it appeared for the first instance) AsiSoaHost_(dbname) services are started.
7. Create a new iMIS Desktop shortcut for use with the second instance. Make a copy of the existing iMIS Desktop shortcut under Start > Programs > ASI > iMIS > iMIS Desktop. Right-click iMIS Desktop and select Send to Desktop, create shortcut.
8. Rename this shortcut to iMIS_2 (or whatever you are calling the second instance) and then right-click it and select Properties. Change the path in both Target and Start In to point to the second instance folder ("C:\Program Files\ASI_2\iMIS\Omnis7\Omnis7.exe" imis4.lbr /m) and ("C:\Program Files\ASI_2\iMIS\").
9. Test access to the new iMIS_2 application with iMIS Desktop.
□ Open iMIS Desktop but do not log on! Click Cancel.
□ Select Logon > Set Host Location. The Local Preferences window appears.
□ Click Insert. The Application Server URL Setup window appears.
□ In the Server field, specify the URL for the new iMIS_2 application that you created earlier (for example, http://(servername)/iMIS_2), and click Save.
Note: As of release 15.2.10, the URL to iMIS Desktop must end with /CS.
□ Click Edit, and from the Application Servers list, choose the URL for the new iMIS_2 application.
□ Click OK and close the Local Preferences window.
□ Select Logon > Logon to Host. The Server field indicates the URL for the new iMIS_2 application.
□ Log on as MANAGER and ensure that Desktop is working properly for the new instance of iMIS.
Note: If you receive a SQL Login error, close iMIS Desktop and run the DBMaintenance.exe utility that is located in the new ASI_2 folder structure (C:\Program Files\ASI_2\iMIS\net\iMISDBUpgrade). Use the iMIS SQL Server login credentials to connect to the new iMIS database for this instance of iMIS. When the iMIS Database Repair window appears, click Prepare iMIS Database. Wait for a successful completion message, and then close the utility and log on with iMIS Desktop again.
10. Perform the post-install configuration tasks listed in the Installation Guide.
11. Test access to the iMIS_2 application from the staff view.
□ Open a supported browser.
□ Go to
the URL for iMIS_2 (for example, http://(servername)/iMIS_2).
If the iMIS Home page appears,
connections to iMIS_2 are working properly.
□ Click Log On and verify that you can log on as MANAGER.
12. (Public view) Test access to the iMISpublic_2 application with a web client.
□ Open a supported browser.
□ Go to
the URL for iMISPublic_2 (for example, http://(servername)/iMISPublic_2).
The public welcome
page for iMIS appears.
□ Click Log On and verify that you can log on as MANAGER, which means connections to iMISPublic_2 are working properly.
13. (CM Only) Manually change the URL and other paths as needed for your second instance WCM site.
14. (CM Only) Regenerate all currently published content by going to the new instance's appserver:
□ From Content Management, select Content designer > Manage content, and select the root @ folder.
□ Click Publish, select Publish Working Items, Regenerate Published Items, and click OK.